Display of system information

ABSTRACT

A method for organizing and displaying management information regarding the hardware and software components in a computer network. The invention organizes the data into major component groups and displays these groups and their devices in clear, descriptive language. The method comprises a plurality of operational parameters about different components in a computer network. The operational parameters are organized into a plurality of hierarchical levels. The method further comprises a plurality of forms which enable the modification of one or more of the operational parameters. Each of the forms correspond to one of the hierarchical levels.

RELATED APPLICATIONS

The subject matter of U.S. patent application entitled "SystemManagement Graphical User Interface," filed on Oct. 1, 1997, applicationSer. No. 08/943,357, and having attorney Docket No. MNFRAME.028A isrelated to this application.

PRIORITY CLAIM

The benefit under 35 U.S.C. § 119(e) of the following U.S. provisionalapplication(s) is hereby claimed:

    ______________________________________                                                           application                                                Title              Ser. No.  Filing Date                                      ______________________________________                                        "High Performance Network Server                                                                 60/046,310                                                                              May 13, 1997                                     System Management Interface"                                                  ______________________________________                                    

APPENDICES

Appendix A, which forms a part of this disclosure, is a list of commonlyowned copending U.S. patent applications. Each one of the applicationslisted in Appendix A is hereby incorporated herein in its entirety byreference thereto.

The microfiche appendix, consisting of one sheet of 31 frames, whichforms a part of the disclosure of this patent application, is a copy ofthe definition of the NF9000 MIB Definitions and is entitled "Appendix6: NF9000 MIB Definitions."

COPYRIGHT RIGHTS

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The present invention relates to the organization and display of dataabout components in a computer network. Specifically, the presentinvention is an apparatus and method for obtaining, organizing ordisplaying data related to network components.

BACKGROUND OF THE INVENTION

Simple Network Management Protocol

Computer network management systems use a standardized communicationprotocol to facilitate communication between devices (computers,printers, peripherals) on the network. The standardized communicationprotocol discussed with this invention is known as the Simple NetworkManagement Protocol (SNMP). SNMP is explained in more detail in TheSimple Book by Marshall T. Rose, 2d ed, Prentice-Hall, Inc., 1994, whichis hereby incorporated herein by reference. The SNMP acts as a mechanismto provide and transport management information between networkcomponents. SNMP is recognized as an industry standard for networkmanagement.

Whenever a program at the user site sends a request to a program at theserver site and waits for a response, the requesting program is calledthe "client" and the responding program is called the "server." Innetwork Server management systems, the user (usually a networkadministrator) uses a software module known as an SNMP manager tomonitor and manage the server or servers in a network. The SNMP managersends commands and receives information through the network from asoftware module called a SNMP agent, which directly monitors the serverthrough device drivers and other components. For example, an SNMPmanager may request, from the SNMP agent, information regarding theamount of unused memory on a memory module. The SNMP manager and theSNMP agent can be on the same workstation, or the SNMP manager can be ata remote location.

SNMP uses a transport protocol stack such as User DatagramProtocol/internet Protocol (UDP/IP) or Transmission ControlProtocol/Internet Protocol (TCP/IP). UDP/IP provides connectionlesscommunication over user Internet Protocol services. It is part of theTCP/IP suite. UDP/IP operates at the transport layer, and in contrast toTCP/IP, does not guarantee the delivery of data. TCP/IP is standardInternet protocol (or set of protocols) which specifies how twocomputers exchange data over the Internet. TCP/IP handles issues such aspacketization, packet addressing, handshaking and error correction. Formore information on TCP/IP, see Volumes I, II and III of Comer andStevens, Internetworking with TCP/IP, Prentice Hall, Inc., ISBNs0-13-468505-9 (vol. I), 0-13-125527-4 (vol. II), and 0-13-474222-2 (vol.III).

Upon receiving a data request by a user, the SNMP manager opens one ormore SNMP sessions and formulates a proper information request for SNMPagent. The SNMP manager is the client and the SNMP agent is the server.The SNMP manager may be generic or specifically designed for theparticular server type.

Typically, the SNMP manager has several parts, each performing adifferent function. But these parts are related and work together toaccomplish certain tasks.

SNMP Management Information Base

When formulating the information request, the SNMP manager may use a setof variables called the Management Information Base (MIB). In general,an MIB defines the aspects of the system and/or the components in thesystem, such as a disk drive or a memory module. The MIB also containsnumeric identifiers which tell system components how to access eachvariable. The MIB is a hierarchal collection of variables and thedescription of each variable related to the hardware and softwarecomponents of the network.

Using the variable set of the MIB, the SNMP manager creates aninformation request which is sent to the SNMP agent.

Disadvantages of Existing Server Management Applications

Many existing network and server management applications can read anddisplay SNMP MIB data. With the popularity of user-interface platforms,such as Windows NT and Windows 95, many of these applications use thefeatures of Windows NT and Windows 95 platforms to display SNMP MIBdata. Examples include the "HP Openview" manufactured by HewlettPackard, the "LAN Desk Manager" manufactured by Intel, and "ObjectView"in the Unicenter TNG Total Enterprise Management Suite manufactured byComputer Associates International.

Currently, some network management applications have a main window whichis split vertically into two parts (two-pane window) to display SNMP MIBdata. Typically, the left pane contains the SNMP MIB of the server,while the right pane displays the values of the SNMP MIB variables inplain text or in columns.

While these network management applications display SNMP MIB data, theyare cumbersome and non-intuitive. In real-world situations whereperformance time is critical, these applications fail to provide theuser quick access to information concerning the network.

First, in current systems when the network administrator needs specificinformation about the network, the prior inventions are difficult toaccess because the MIB variables on the left pane may not be displayedor organized in an intuitive manner. The user cannot quickly browse andfind a particular component group or a specific device.

Adding to the problem is the ambiguous descriptions of the MIBvariables. For example, in the "ObjectView" application of the UnicenterTNG Total Enterprise Management Suite, the user may not know what theMIB variable "Rmtntrfce Controller Revision I" represents. Thisinefficiency is more significant when the user needs to access keyvariables quickly in order to react to a malfunction detected on thenetwork.

Minimizing computer server downtime is a major concern in computernetwork systems. With emerging Internet, intranet and collaborativeapplications taking on more essential business roles every day, the costof network server downtime will continue to spiral upward.

Furthermore, some MIB variables, such as entries in a table, are notaccessible to the user because they are used internally by the networkmanagement software. In addition, MIB variables are read-only and cannotbe modified by the user. Many of the prior server managementapplications show the entire MIB--all the variables in the MIBregardless of their status. This creates user confusion. Further, thevalue of the MIB variable is unknown, the value may be displayed on theright pane as "????" or "Not Available."

In other cases, the right pane only displays two or three variables at atime, instead of simultaneously showing all the critical or relatedvariables that the user needs. Consequently, a user may need to proceedvariable by variable. This is highly inefficient. Users often needimmediate access to several distinct variables or a group of variablesto make a decision regarding network problems. Reducing the time toaccess key variables is especially important when the user needs toperform emergency tasks.

Moreover, even when two or three MIB variable values are displayedtogether on the right pane, not all variables important to the user maynot be grouped together. For example, two important variables may beseparated by three or four unimportant variables such as "serial number"or "description." Since the right pane of the window only shows two orthree variable values at a time, the user must use the scroll bars tojump back and forth to compare the values of the important variables.

In addition, the MIB variables are often displayed in nondescriptcolumns on the right without an explanation of what the MIB variablerepresents. As in the example above, for the left part of the window,the user may not know what the MIB variable "Rmtntrfce ControllerRevision I" represents. If the user is unfamiliar with the variablenames, he or she must spend time to look up the variables in usersupport manuals. Again, this inefficiency is more pronounced in criticalsituations when there is a malfunction on the server.

Still further, the values for each MIB variable may not be labelled inthe right pane of the window. The user may not know the units of thevalues. For example, in some of the "ObjectView" application of theUnicenter TNG Total Enterprise Management Suite, the value of a memorysize variable is not labelled. Again, the user must look up the variablein a support manual.

In addition, in many of these prior applications, such as the"ObjectView" application of the Unicenter TNG Total EnterpriseManagement Suite, it is time-consuming to change the values of MIBvariables. In order to change the value of a MIB variable, the user mayneed to click on the right button of the mouse, which opens a separatemenu list box, and select the menu item to change variables. This opensanother dialog box in which the user actually changes the variable. Theuser must close this dialog box in order to return to the servermanagement application. The user must repeat this operation each timethe user needs to change more than one variable. This can betime-consuming and degrade network performance, particularly if thenetwork administrator needs to change a series of variables.

Furthermore, it is often unclear which MIB variables can be changed andwhich cannot be changed. The user must determine which variables areread-write and which are read-only by trial and error or by looking upthe variable in a support manual.

Extra time spent training personnel on how to operate the servermanagement application leads to increased costs and lost productivity.Efficiency becomes even more crucial for companies which have largenetworks and where timing is critical, such as airlines and banks. Anetwork administrator may need to quickly find and modify different MIBvariables for different servers. For example, an airline network mayhave several servers where timing, number of transactions, and size oftransactions are different for each server. An airline may use oneserver for managing ticket sales, one server to handle frequent flyertransactions, and another server to handle arriving flight information.Each server may have its own type of network components, response times,backup systems, etc. Quick access to a server's information could save acompany significant sums.

SUMMARY OF THE INVENTION

The present invention provides a method for displaying informationregarding components in a computer network. The method comprises aplurality of operational parameters about different components in acomputer network. The operational parameters are organized into aplurality of hierarchical levels. One embodiment of the method furthercomprises a plurality of forms which enable the modification of one ormore of the operational parameters. Each of the forms correspond to oneof the hierarchical levels. One embodiment of the method furthercomprises a display module existing in a computer. The display modulefurther comprises a first display pane configured to display thehierarchical levels. The first display pane is further configured toenable the selection of one of the hierarchical levels. The displaymodule further comprises a second display pane configured display theform corresponding to the selected hierarchical level.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a high-level architectural overview of a networkmanagement system in accordance with one embodiment of the invention.

FIGS. 2A and 2B illustrate an organization data structure in oneembodiment of the present invention.

FIG. 3 illustrates the hierarchal organization of network data variablesin one embodiment of the invention.

FIG. 4 illustrates a module-level architecture in accordance with oneembodiment of the invention.

FIG. 5 illustrates a network map window in one embodiment of the claimedinvention.

FIG. 6 illustrates a system management window in one embodiment of thepresent invention.

FIG. 7 illustrates the process of creating a network map window in oneembodiment of the invention.

FIG. 8 illustrates the process of identifying network servers in oneembodiment of the present invention.

FIG. 9 illustrates the network data display process in one embodiment ofthe present invention.

FIG. 10 illustrates the process of retrieving network data anddisplaying a hierarchal tree in one embodiment of the present invention.

FIG. 11 illustrates the series of commands executed in the process ofIretrieving and displaying network data in one embodiment of the presentinvention.

FIGS. 12A and 12B illustrate the process of retrieving data from anetwork server in one embodiment of the present invention.

FIG. 13 illustrates the process of modifying network data values in oneembodiment of the invention.

FIG. 14 illustrates one embodiment of a system information window.

FIG. 15 illustrates one embodiment of a dual-pane window which displaysdata about dual interface memory modules.

FIG. 16 illustrates one embodiment of a window for a single dualinterface module device.

FIG. 17 illustrates one embodiment of a cooling subsystem window.

FIG. 18 illustrates one embodiment of a general system board fanswindow.

FIG. 19 illustrates one embodiment of a window for a single system boardfan device.

FIG. 20 illustrates one embodiment of a general temperature sensorswindow.

FIG. 21 illustrates one embodiment of a window for a single temperaturesensor device.

FIG. 22 illustrates one embodiment of a general power subsystem window.

FIG. 23 illustrates one embodiment of a general power supplies groupwindow.

FIG. 24 illustrates one embodiment of a window for a single power supplydevice.

FIG. 25 illustrates one embodiment of a general CPU subsystem window.

FIG. 26 illustrates one embodiment of a general processors window.

FIG. 27 illustrates one embodiment of a window for a single processordevice.

FIG. 28 illustrates one embodiment of a general adapters window.

FIG. 29 illustrates one embodiment of a window for a single adapterdevice.

FIG. 30 illustrates one embodiment of a general drivers window.

FIG. 31 illustrates one embodiment of a window for a single driverdevice.

FIG. 32 illustrates one embodiment of a general slot subsystem window.

FIG. 33 illustrates one embodiment of a general slot group window.

FIG. 34 illustrates one embodiment of a window for a single slot device.

FIG. 35 illustrates one embodiment of a general slot fans group window.

FIG. 36 illustrates one embodiment of a window for a single slot fandevice.

FIG. 37 illustrates one embodiment of a general canister group window.

FIG. 38 illustrates one embodiment of a general canister subgroupwindow.

FIG. 39 illustrates one embodiment of a window for a single canisterdevice.

DETAILED DESCRIPTION OF THE INVENTION

Most Windows NT or Windows 95 users are familiar with dialog boxes andhow to view (scroll bars) and change variables. Dialog boxes alsoaggregate related fields of data in a single display window. Oneembodiment of the present invention takes advantage of this familiaritywith dialog boxes to display SNMP MIB data in an organized,easy-to-navigate format. The network administrator (the user) can browseand modify all the data fields related to a MIB group in a singlewindow.

One embodiment of the present invention allows the user to "browse"through the MIB-defined variables of a computer network. Essentially,the MIB data is a hierarchal collection of data concerning all thehardware and software components in the computer network.

Architectural Overview

FIG. 1 illustrates a high level architectural overview of a networkmanagement system appropriate for use with one embodiment of theinvention. In one embodiment of the invention, the client and servercomputers 102 and 136 are on multi-processor Pentium Pro-based computershaving 256 megabytes or more of RAM. It will be apparent to those ofordinary skill in the art, however, that the computers 102 and 136 maybe any conventional general purpose single- or multi-chip microprocessorsuch as a Pentium processor, a Pentium Pro processor, a 8051 processor,a MIPS processor, a Power PC processor, an ALPHA processor, etc. Inaddition, the computers 102 and 136 may be any conventional specialpurpose microprocessor such as a digital signal processor or a graphicsprocessor.

In one embodiment of the present invention, the server 136 is an NF9008(also known as NF9000-T) manufactured by NetFRAME Systems Incorporatedof Milpitas, Calif. The NF9008 series are fault-tolerant,standards-based servers, which have multiple peripheral componentinterconnect (PCI) card slots for one or more adapters. In anotherembodiment of the present invention, the server 136 is an NF9016 (alsoknown as an NF9000-C), which has multiple canisters or fault isolationunits (FlU). These canisters are boxes which may each contain more thanone PCI adaptor card slots. Multiple card slots and multiple canistersallow the user to remove or add adapters to the server 136 while theserver 136 and operating system continue to run.

At the user (or client) side, the SNMP manager 108 displays data to theuser through a communication layer that organizes the data into datastructures. When the SNMP manager 108 receives a command from the user,it calls a standard Windows SNMP Library of objects 112, which sendsmessages using an SNMP protocol stack 114, such as UDP/IP, to the SNMPagent 128 via a network of drivers 116, adapters 118, and network medium120.

In one embodiment of the present invention, the system managementgraphical user interface application is contained in a software module107 which operates with the SNMP manager 108. In one embodiment, thesoftware module 107 is called Maestro Central 107 manufactured byNetFRAME Systems Incorporated of Milpitas, Calif. Maestro Central 107may be used in a Microsoft Windows environment. Maestro Central 107 maysend instructions to the SNMP manager 108.

At the server side, the SNMP agent 128 retrieves information detected inthe server 136. If there is more than one server 136 in the network,then there is an SNMP agent 128 associated with each server 136.

In one embodiment of the present invention, the SNMP agent 128 retrievesinformation from device drivers 124 and a self-contained network ofdistributed service microprocessors called Intrapulse 122. Intrapulse122 is manufactured by NetFRAME Systems Incorporated of Milpitas, Calif.This self-contained network continuously monitors and manages thephysical environment of the server, regardless of the operational statusof the server 136 (a component of the server 136 may be malfunctioning).The SNMP agent 128 also sends messages to the SNMP manager 108 via anetwork of drivers 132, adapters 134, and network medium 120.

Overview of Module-level Structure and Description of Modules

An `object` as used here and in object-oriented programming is avariable that may comprise both routines (methods) and data. An objectis treated as a discrete entity and may have its own address. Someobjects, may only contain data and no routines.

A `class` as used here is a blueprint of an object. From a class withspecified properties, methods, and functions, the application can createobjects with those same properties, methods, and functions. Once theobject is created, the application can modify the properties of theobject and the data in the object. An application can use multipleobjects of the same class. A class may also be used to describe a groupof objects sharing the same properties, etc.

Objects and classes are explained in more detail in Object Programmingwith Visual Basic4 by Joel P. Dehlin and Matthew J. Curland, MicrosoftPress, 1996, and Computer Dictionary by collective authors, MicrosoftPress, 1991, which are hereby incorporated herein in its entirety byreference.

In the following description of one embodiment of the invention, a`module` includes, but is not limited to, software or hardwarecomponents which perform certain tasks. Thus, a module may includeobject-oriented software components, class components, procedures,methods, functions, subroutines, data structures, segments of programcode, drivers, firmware, microcode, circuitry, data, data structures,tables, arrays, etc. In addition, those with ordinary skill in the artwill recognize that a module can be implemented using a wide variety ofdifferent software and hardware techniques. A module may also mean apublished report by a group of experts defining MIB objects for aparticular area of technology. RFC 1213, Management Information Base forNetwork Management of TCP/IP-based Internets: MIB-IIcontains a moduledefining the basic objects needed to manage a TCP-IP network.

FIG. 4 illustrates a module-level architecture in accordance with oneembodiment of the invention. The "start application" block 400 is thefirst step where all modules and dialog boxes used for one embodiment ofthe present invention are created. In one embodiment of the invention,this application is a C++ class file called "maestro2.ccp."

The CMainFrame Class 408 creates all the windows and graphical userinterfaces used in one embodiment of the present invention. This is alsoknown as the Microsoft Foundation Class Document/View Architecture. TheDocument Class 410 keeps the data about the application. The View Class412 displays to the user a representation of the data kept in theDocument Class 410 which is defined by Microsoft Corporation. The use ofthese classes is explained in more detail in Inside OLE, 2d edition,1995 by Kraig Brockschmidt, which is hereby incorporated herein in itsentirety by reference.

The MIB Manager Module 402 may perform a number of functions in oneembodiment of the invention. The MIB Manager Module 402 may manage theother modules which retrieve and display MIB data. The MIB ManagerModule 402 may contain one or more "retrieve data" functions. In oneembodiment, the MIB Manager Module 402 calls the MIB Section Module 404and the NF MIB Variable Module 406 to retrieve and temporarily store MIBdata retrieved from the server 136. The MIB Manager Module 402 may alsocall other modules to implement the user's changes to read-write MIBvariables.

The MIB Section Module 404 may be used to retrieve MIB data contained ina table or organized in a group of variables in one embodiment of theinvention. The MIB Section Module 404 may contain "retrieve data" and/or"retrieve table data" functions. The MIB Section Module 404 may also beused to store retrieved MIB data and/or MIB table data.

The MIB Variable Module 406 may be used to retrieve MIB data in oneembodiment of the invention. The MIB Variable Module 406 may contain"retrieve variable data" functions. The MIB Variable Module 406 may alsobe used to store retrieved MIB data.

The Microsoft Windows NT/95 Timer Module 430 may be used to set the timeinterval between each data retrieval from the server 136 in oneembodiment of the invention. This is useful for dynamic variables suchas fan speed. In one embodiment of the invention, the Timer Module 430is used to set the interval between retrievals for data that is notcurrently being displayed to the user. For example, if the user isviewing the fan speed for fan number 1, as shown in FIG. 19, then thetemperature detected by temperature sensor number 1, as shown in FIG.21, is not currently being displayed to the user. The user may configurethe time interval between data retrievals from temperature sensor number1 by going to the "Window" menu 514 and pulling down the menu item "UserOptions." This opens a User Options dialog box which allows the user tomake the change. The user may change the data retrieval time intervalfor all MIB variables not currently being displayed. In one embodimentof the invention, the user may configure this interval to a desired timeduration, such as a half hour, an hour, etc.

The Server Module 418 may contain information about the server 136 inone embodiment of the invention. The Server Module 418 may containinformation on how to display the server 136 as an icon on the SystemManagement Window 602 in one embodiment of the invention.

The Network Map Window Module 422 may perform a number of functions inone embodiment, including displaying the Network Map Window 502 and eachserver 136 in the network as an icon 506 in the Network Map Window 502as shown in FIG. 5. The Network Map Window Module 422 may call theEnumServer Module 414 to discover the names and number of servers 136 inthe network 120.

The EnumServer Module 414 discovers and identifies the number of servers136 in the system in one embodiment of the invention. The EnumServerModule 414 may store information in the memory of the microprocessor102. The EnumServer Module 414 is a local module, but it is global inthe sense that it is accessible from anywhere in the system. Forexample, if there are multiple servers, the EnumServer Module 414 mayact as a repository of server information.

The SNMP Module 416 is a class that encapsulates all the SNMP functionsused by one embodiment of the present invention, such as "GET," "GETNEXT," and "SET." The GET function is typically used by the SNMP agent128 to retrieve non-table SNMP MIB data from the server 136 in responseto a request by the SNMP manager 108.

The GET NEXT function is typically used to retrieve more than onevariable, such as a table of variables. In one embodiment of theinvention, it is difficult for the SNMP manager 108 to predict thenumber of entries in a MIB table. The GET NEXT function gets the valueof the variable requested by the user and also the object identifier ofthe next variable. Often, a loop is created with GET NEXT until allrequested values are retrieved. If all variables in a table areretrieved, the GET NEXT function returns an object identifier that is"outside" the table. The SNMP manager 108 uses this value to determineif it has completed retrieving all data that is in a table. The SETfunction is used by the SNMP manager 108 to change values of MIBvariables stored on the SNMP agent 128.

In one embodiment of the invention, the MIB 110 contains a hierarchalcollection of variables related to the hardware and software componentsof the server 136. Using the MIB variables, the SNMP manager 108 (morespecifically, the SNMP Module 204) creates an information request whichis sent to the SNMP agent 128. In one embodiment of the invention, theserver is a NF9000 server. A SNMP MIB for the NF9000 series is set forthin Appendix B.

The SNMP Window Module 420 is used to pass messages among applications.The SNMP Window Module 420 allows an application, such as a systemmanager, to communicate with the SNMP module 204. The use and operationof an SNMP Window Module 420 is well known to those of ordinary skill inthe art.

Creating and Displaying the Network Map Window 502

FIG. 7 illustrates the start application process in one embodiment ofthe invention. To start the application, the user activates"maestro2.ccp" (herein referred to as "Maestro" 400), a C++ class file.

Maestro 400 calls standard Microsoft initialization modules to performstandard housekeeping functions. This is shown in block 704. Maestro 400also calls or initializes a standard dynamic link library (DLL) such asthe Windows SNMP (WinSNMP) DLL (WinSNMP Library) 706 manufactured byAmerican Computer Electronic Corporation. The WinSNMP Library is used todo SNMP transactions while an application, such as Maestro 400, isrunning. DLLs execute under the Microsoft Windows NT or Windows 95operating systems.

Maestro 400 creates (1) a Microsoft Foundation Class Document/ViewArchitecture (MFC Doc/View Architecture) 408 shown in block 708; (2) anEnumServer Module 414 shown in block 722 and FIG. 8; (3) an SNMP Module416 shown in block 718; (4) a MIB Manager Module 402; (5) a MIB SectionModule 404; and (6) a MIB Variable Module 406. These modules are furtherexplained in detail.

The MFC Doc/View Architecture shown in block 708 creates all the windowsand graphical user interfaces used in one embodiment of the presentinvention. Specifically, the CMainFrame Class 408 creates the DocumentClass 410 in block 712 and the View Class 412 in block and 714. Asdescribed above, the Document Class 410 keeps the data about theapplication, and the View Class 412 displays to the user arepresentation of the data kept in the Document Class 410. TheCMainFrame Class 408 creates the actual Network Map Window 502 andSystem Management Window 600 and its associated forms as shown in FIGS.14 through 39. FIG. 5 illustrates the Main Window 500 in one embodimentof the invention and the Network Map Window 502 where the user mayaccess the system manager application.

The Network Map Window Module 422 calls the EnumServer Module 414 todiscover the number of servers 136 in the network 120 and the names ofeach server 136. This is shown in FIG. 8. In block 802, the EnumServerModule 414 keeps looking for servers 136 on the network 120 until allare found. In one embodiment of the invention, the EnumServer Module 414looks for NetFrame servers and creates a Server Address Module 428 foreach NetFrame server. This is shown in blocks 804 through 808. After theEnumServer Module 414 finds the name and address of a server 136, theNetwork Map Window Module 422 displays the name 512 and the address 510of the server 136 on the Network Map Window 502. This is shown in block810. When there are no more servers on the network 120, the EnumServerModule 414 ends its discovery process, as shown in block 812.

Maestro 400 also creates an SNMP Module 416 in block 718. The SNMPModule 416 creates an SNMP Window Module 420 as shown in block 720. Inone embodiment of the invention, the SNMP Window Module 420 may be usedby the WinSNMP Library and Microsoft Windows to pass messages betweenapplications. The WinSNMP Library uses a window to transact SNMPmessages. In one embodiment of the invention, Maestro 400 may use a`hidden` window, which is not visible on the user's desktop while theapplication is running. The SNMP Window Module 420 allows anapplication, such as a system manager, to communicate with the SNMPitself.

Maestro 400 also creates the EnumServer Module 414 shown in block 722.The EnumServer Module 414 is empty at this point, but it is made globalfor future access from anywhere in the system. When the application isrunning, there may be certain information that is constantlyextrapolated by different parts of the system. For example, there may bemultiple servers that require the same or similar data. This informationis stored locally in a central location such as the EnumServer Module414. Thus, the EnumServer Module 414 acts as a repository.

In one embodiment of the present invention, the EnumServer Module 414discovers the names and the numbers of NetFRAME servers on the networkand stores this information in an EnumServer Module list as shown inblock 808.

Creating and Displaying the System Management Window 600

In one embodiment of the present invention, the user may access theSystem Management Window 600 from the Network Map Window 502. FIG. 9illustrates the module-level process of how the user starts the systemmanagement application in one embodiment of the present invention.

Specifically, when the user double-clicks on a server icon 506 or theserver name 512 in the Network Map Window 502, Maestro 400 creates theSystem Management Window 600 and calls the Server Module 418, the MIBManager Module 402, the MIB Section Module 404, and the MIB VariableModule 406, as shown in blocks 900 through 908. In block 910, Maestro400 displays the System Management Window 600.

In one embodiment of the invention, the Server Module 428 may be used tostore information about the server 136, such as the name and address ofthe server 136. The Server Module 428 may contain information on how todisplay the server 136 as an server icon 606 on the System ManagementWindow 602 in one embodiment of the invention.

After the Server Module 420 and the MIB Manager Module 402 are created,Maestro 400 displays the System Management Window 600 as shown in FIG. 6of one embodiment of the invention. All server management functions maybe provided through this window. In one embodiment of the invention, theSystem Management Window 600 is divided into a left part 602 and a rightpart 604. In one embodiment of the invention, a `MIB Tree` is displayedin the left part 602.

FIG. 2 illustrates the MIB Tree in one embodiment of the presentinvention. The MIB Tree is simply the name 200 of the server 136, theserver type 202, and the major subsystems of the server 136. In oneembodiment of the present invention, the type of server 136 is a NF9000manufactured by NetFRAME of Milpitas, Calif. The subsystems may includethe overall System Group 204 the Cooling Subsystem 206, the PowerSubsystem 208, the CPU Subsystem 210, the Adapter Group 212, the DriverGroup 212, the Slot Group 216, the Slot Fan Group 218, and the CanisterGroup 220.

The `root` level of the tree is the name 200 of the server 136, and thedifferent sections are the `child` branches 204 through 220 of the root.If a group has subgroups or contains more than one device, then it willcontain "child" branches for those subgroups or devices. For example,the Cooling Subsystem 206 has two subgroups: the Fans 226 and theTemperature Sensors 230. The Fans subgroup 226 then has child branchesfor individual fans 228.

Creating and Displaying Forms for Subsystems in the MIB Tree

FIG. 10 illustrates the module-level process of retrieving anddisplaying the MIB Tree and its associated forms in the SystemManagement Window 600 in one embodiment of the present invention. Inblock 1000, the MIB Manager Module 402 calls the SNMP Module 416 to getMIB data from the network 120 using the MIB Section Module 404. In block1002, the SNMP Window Module 416 then displays the server name 200 inthe left part 602 of the System Management Window 600. In blocks 1004and 1006, the MIB Manager Module 402 looks for the server's majorsubsystems using the MIB Section Module 404. These subsystems aredisplayed under the server name 606 and the type of server 608. TheSystem Management Window 600 also displays icons of the eight majorsubsystems on the right part 604 of the window.

The user may double-click on the icons on either the left part 602 orthe right part 604 of the System Management Window 600 to access thesubgroups and individual devices. FIG. 11 illustrates the series ofcommands executed in the process of retrieving and displaying MIB datain forms in the system management window in one embodiment of thepresent invention. In block 1102, the MIB Manager Module 402 creates theform corresponding to the user's selection. After the appropriate formis created, the MIB Manager Module 402 calls the SNMP Window Module 420and the Network Map Window Module 422 to display the form in the rightpart 604 of the System Management Window 600.

For example, if the user clicks on the Cooling Subsystem icon 612 or618, the corresponding form created by the MIB Manager Module 402 is theCooling Subsystem Form in block 1102. FIG. 17 shows one embodiment ofthe Cooling Subsystem Form in the right part 604 of the SystemManagement Window 600. In block 1106, the MIB data is sorted into datastructures. In block 1108, the SNMP Module 416 gets data from these datastructures to form the static text in the right part 604 of the SystemManagement Window 600. For example, the title "COOLING GROUP" 1600 isstatic text that will not change with time. This text is displayed bythe SNMP Window Module 416 and the Network Map Window Module 422 asshown in block 1102.

Retrieving and Displaying Values for Dynamic MIB Variables

FIGS. 12A and 12B illustrate the module-level process of retrieving datafrom a server 136 in one embodiment of the present invention. The MIBManager Module 402 may contain one or more "retrieve data" functions.This is shown in block 1204. The MIB Manager Module 402 may, in additionor instead, direct other modules to retrieve and display the MIB data.In one embodiment of the invention, the MIB Manager Module 402 calls theMIB Section Module 404 and the MIB Variable Module 406 to retrieve andtemporarily store MIB data retrieved from the server 136. This is shownin blocks 1204 through 1224.

In block 1208 of one embodiment of the invention, the MIB Manager Module402 invokes the MIB Section Module's "retrieve data" function. The MIBSection Module 404 may be used to retrieve MIB data contained in a tableor organized in a group of variables in one embodiment of the invention.The MIB Section Module 404 then queries whether the requested data is asingle variable or a table of variables. If the requested data is atable, the MIB Section Module's "retrieve table data" function isinvoked in block 1214. As shown in block 1216 and 1218, the MIB SectionModule 404 invokes the SNMP Module's GET NEXT function, which continuesto retrieve data until there are no more variables in the MIB table. TheMIB Section Module 404 may also be used to store retrieved MIB dataand/or MIB table data.

If the requested information is not a table, the MIB Variable Module 406may be used to retrieve MIB data in one embodiment of the invention. Asshown in blocks 1222 and 1224, the MIB Variable Module invokes the SNMPModule's GET function, which continues to retrieve data until there areno more MIB variables requested. The MIB Variable Module 406 may be usedto store retrieved MIB data.

In the cooling subsystem 206 example used above, one embodiment ofpresent invention uses variable identifiers within the MIB to retrievedata. When the user clicks on the Cooling Subsystem icon in oneembodiment of the invention, the MIB Section Module 404 and the MIBVariable Module 406 retrieve values for the following MIB variables:

"coolingFanGeneralLED"

"coolingFanMinSpeed"

"coolingFanSpeedSetting"

"coolingMaximumNumberOfSystemFans"

"coolingFanNumber"

"coolingFanSpeed"

"coolingFanFault"

"coolingFanLocation"

"coolingAlertTemperature"

"coolingShutdownTemperature"

"coolingMaximumNumberOfTemperatureSensors"

"coolingSensorNumber"

"coolingSensorTemperature"

"coolingSensorLocation"

Although only the variables for the cooling subsystem 206 are shownhere, the process is the same when the user clicks on any one of theother subsystems or device groups. The MIB Section Module 402 and theMIB Variable Module 406 will retrieve the values of the MIB variablesassociated with those other device groups or subsystems.

After the MIB Manager Module 402 retrieves the values of the requestedMIB variables, the SNMP Window Module 420 may sort the data into datastructures and display the data in dialog boxes in the right part 604 ofthe System Management Window 600. This is shown in block 1226 in oneembodiment of the invention. One embodiment of the invention alsoupdates the values of dynamic variables every five seconds, as shown inblock 1228.

For example, the variable "coolingFanMinSpeed" represents the minimumspeed below which a system board fan is considered malfunctioning in oneembodiment of the invention. This variable is defined in the MIB itselfas shown in FIG. 4. CoolingFanMinSpeed is identified in the MIB as"1.3.6.1.4.1.837.2.3.2.0." The MIB Manager Module 402 uses this numericMIB identifier to invoke the MIB Variable Module 406 which sends arequest to the SNMP agent 128. The SNMP agent 128 retrieves this valueand sends it to the SNMP Module 416. The SNMP Module 416 calls the SNMPWindow Module 420 to display it in a dialog box 1718. The dialog box islabelled "Minimum Speed (below which an alert is generated)" 1608. Thevalue is further labelled "RPS" 1728 (revolutions per second).

In one embodiment of the present invention, the MIB Manager Module 402does not display all of the cooling subsystem MIB variables at once onthe right part 604 of the System Management Window 600. Instead, oneembodiment of the claimed invention only displays the values for thefollowing cooling subsystem variables on the right part 602 of theSystem Management Window 600:

"coolingFanGeneralLED"

"coolingFanMinSpeed"

"coolingMaximumNumberOfSystemFans"

"coolingAlertTemperature"

"coolingShutdownTemperature"

"coolingMaximumNumberOfTemperatureSensors"

These particular MIB variables are displayed together because theyrelate generally to all the components of a particular subsystem orsubgroup instead of a particular device. This is illustrated in FIGS.14, 17, 22, 25, 35, and 37. In FIG. 17, the MIB variables relategenerally to the cooling subsystem. If the user wants to see MIB datafor a particular device, the user may click on either the Fans icon 1702or 1736 or the Temperature Sensors icon 1704 or 1738 on either the left702 or right part 704 of the System Management Window 600.

In one embodiment of the present invention, the values of the MIBvariables are displayed in descriptive dialog boxes with labels such as"RPS" (revolutions per second) 1728 and "Degrees Celsius" 1730 and 1732.

Once MIB data is retrieved from the server 136, the MIB Manager Module402 may update dynamic variables, such as fan speed, which are currentlybeing viewed by the user every five seconds in one embodiment of theinvention. This is shown in block 1228. For dynamic variables that arenot currently being displayed, the user may separately configure theinterval between data retrievals to be any time duration, includingdurations such as a half hour or an hour.

Displaying Child Branches of the MIB Tree

When the user clicks on one of the major subsystem icons 610 through 740in either the left part 602 or the right part 604 of the SystemManagement Window 600 shown in FIG. 7, the SNMP Window Module 420displays the child branches of that subsystem.

In one embodiment of the present invention, the icons labelled "Fans"1702 and "Temperature Sensors" 1704 are displayed as child branchesunder the icon labelled "Cooling Subsystem" 612 on the left part 602 ofthe System Management Window 600. These are two subgroups of MIBvariables in the cooling subsystem 206.

If the user clicks on the child branch labelled "Fans" 1702 under the"Cooling Subsystem" icon 612 on the left part 602 of the SystemManagement Window 600, the SNMP Window Module 420 displays all thesystem board fan icons 1800 as child branches numbered one through n, nbeing the total number of fans, under the icon labelled "Fans" 1702. Forexample, if there are six system board fans in an embodiment of theinvention, then the left part 602 of the System Management Window 600will show "Fan Number 1" 1802, "Fan Number 2" 1804, "Fan Number 3" 1806,"Fan Number 4" 1808, "Fan Number 5" 1810, and "Fan Number 6" 1812.

If the user clicks on child icon labelled "Fan Number 1" 1802 or 1816,in either the left part 602 or right part 604 of the System ManagementWindow 600, the SNMP Window Module 420 displays the form for Fan Number1 as shown in FIG. 19.

Although only the subgroups and individual devices for the coolingsubsystem 206 are discussed here, the process is the same when the userclicks on any one of the other subsystems or device groups. The SNMPWindow Module 420 will display the subgroups and/or individual devicesunder those subsystems or device groups.

Changing the Values for Read-Write MIB Variables

Some MIB variables are read-write in one embodiment of the invention.These variables can be modified by the user and are displayed in whitedialog boxes in the right part 604 of the System Management Window 600.For example, the MIB variable "coolingFanMinSpeed" is modifiable fromthe right part 604 of the System Management Window 600. This is shown inFIG. 17.

FIG. 13 illustrates the module-level process of changing values of MIBvariables in one embodiment of the invention. In block 1300, the usercan change the value of this variable by (1) moving the mouse cursor tothe white area of the dialog box related to Minimum Speed 1718, (2)backspacing or highlighting the current value using the left mousebutton, and (3) typing in the number of a new minimum fan speed. Thisvalue can be anywhere from 0 to 255 as defined by the MIB. A change tothis variable affects all system board fans. After the user enters a newvalue, the user clicks on the "apply" button 1740 in block 1302. Asshown in blocks 1306 and 1308, the MIB Manager Module 402 and the SNMPWindow Module 420 displays an error dialog box if the user enters anumber outside the defined range for the MIB variable in one embodimentof the invention.

In one embodiment of the invention, the MIB Manager Module 402 maymodify the MIB variable itself or it may call other modules to implementthe user's changes. In one embodiment of the present invention, the MIBManager Module 402 may call the SNMP Module 416 to use its "set"function to change a read-write variable. The MIB Manager Module 402 mayalso call the MIB Section Module 404 and/or the MIB Variable Module 406to implement the change.

Advantages of the Present Invention

First, one advantage of the present invention is that the subsystems ofthe server 136 are organized in an easy-to-access and efficient manner.There are only eight subgroups in one embodiment. Unlike priorinventions, one embodiment of the present invention keeps the left part602 of the System Management Window 600 unfettered with unduly confusingsubheadings and variables. At a glance, the user can quickly see themajor components of the server in one embodiment of the invention andselect a subsystem in which to probe further. This saves the networkadministrator time and improves the overall network productivity.

Furthermore, each MIB subsystem, subgroup, and device are clearlyidentified in the present invention. There are no ambiguous variablessuch as "Rmtntrfce Controller Revision I." The network administratordoes not need to learn new variables or refer to software manuals. Thepresent invention removes the focus of the user from the interfaceformat and allows the user to concentrate on the information itself.This further saves time and improves productivity.

Another advantage of one embodiment of the invention is that the MIBManager Module 402 does not display the entire MIB, unlike priorinventions. In other words, one embodiment of the invention does notdisplay the variables in the MIB that are not accessible to the user.Instead of generating a "???" entry or a "Not Available," the presentinvention reduces user confusion and saves window space by notdisplaying these MIB variables at all. For example, in one embodiment,the MIB variable "coolingFanTableEntry" is not accessible to the user sothe embodiment does not display this variable.

Second, the present invention displays all data related to a subsystemor all data related to an individual device in a single window on theright part 604 of the System Management Window 600. For example, oneembodiment of the present invention displays "Minimum Speed (below whichan alert is generated)," "Alert Temperature" and "Shutdown Temperature"in the same window. The user does not have to use scroll bars to move upand down or left and right to find and compare related variables as inprior inventions. This allows the network administrator to comparevalues quickly and make a decision. This becomes particularly importantin time-critical applications, where network administrators need to makequick assessments about the network server and act accordingly.

Third, the MIB variables in one embodiment of the present invention areclearly described on the right part 604 of the System Management Window600. For example, "Minimum Speed" is accompanied by the description"(below which an alert is generated)." The user does not need to look upthe variable in a software manual. This saves time for the networkadministrator, particularly in time-critical situations.

Fourth, the values for each MIB variable is labelled in one embodimentof the invention. For example, fan speed is labelled "RPS" 1728(revolutions per second) and temperature is labelled "Degrees Celsius."The user does not need to make guesses or look the variables up in asupport manual.

Fifth, the user can navigate and change MIB data in the SystemManagement Window 600 itself by pointing and clicking at the valueitself, such as "Alert Temperature" 1720. The user does not need to openand close any other dialog box or menus. This saves the user valuableadministration time, especially if the user needs to modify a list ofvariables.

Furthermore, the variables that can be changed by the user are clearlyshown in white boxes in one embodiment of the present invention. Thissaves the user time from guessing which variables can be modified.

While the above detailed description has shown, described and pointedout the fundamental novel features of the invention as applied to apreferred embodiment, it will be understood that various omissions,substitutions and changes in the form, and details of the illustrateddevice may be made by those skilled in the art without departing fromthe spirit of the invention. Consequently, the scope of the inventionshould not be limited to the foregoing discussion but should be definedby the appended claims.

    __________________________________________________________________________    Title              Application No.                                                                        Attorney Docket                                   __________________________________________________________________________    "System Architecture for Remote                                                                  08/942,160                                                                             MNFRAME.002A1                                     Access and Control of Environmental                                           Management"                                                                   "Method of Remote Acess and                                                                      08/942,215                                                                             MNFRAME.002A2                                     Control of Environmental                                                      Management"                                                                   "System for Independent Powering of                                                              08/942,410                                                                             MNFRAME.002A3                                     Diagnostic Processes on a Computer                                            System"                                                                       "Method of Independent Powering of                                                               08/942,320                                                                             MNFRAME.002A4                                     Diagnostic Processes on a Computer                                            System"                                                                       "Diagnostic and Managing Distributed                                                             08/942,402                                                                             MNFRAME.005A1                                     Processor System"                                                             "Method for Managing a Distributed                                                               08/942,448                                                                             MNFRAME.005A2                                     Processor System"                                                             "System for Mapping Environmental                                                                08/942,222                                                                             MNFRAME.005A3                                     Resources to Memory for Program                                               Access"                                                                       "Method for Mapping Environmental                                                                08/942,214                                                                             MNFRAME.005A4                                     Resources to Memory for Program                                               Access"                                                                       "Hot Add of Devices Software                                                                     08/942,309                                                                             MNFRAME.006A1                                     Architecture"                                                                 "Method for The Hot Add of Devices"                                                              08/942,306                                                                             MNFRAME.006A2                                     "Hot Swap of Devices Software                                                                    08/942,311                                                                             MNFRAME.006A3                                     Architecture"                                                                 "Method for The Hot Swap of                                                                      08/942,457                                                                             MNFRAME.006A4                                     Devices"                                                                      "Method for the Hot Add of a Network                                                             08/943,072                                                                             MNFRAME.006A5                                     Adapter on a System Including a                                               Dynamically Loaded Adapter Driver"                                            "Method for the Hot Add of a Mass                                                                08/942,069                                                                             MNFRAME.006A6                                     Storage Adapter on a System Including                                         a Statically Loaded Adapter Driver"                                           "Method for the Hot Add of a Network                                                             08/942,465                                                                             MNFRAME.006A7                                     Adapter on a System Including a                                               Statically Loaded Adapter Driver"                                             "Method for the HotAdd of a mass                                                                 08/962,963                                                                             MNFRAME.006A8                                     Storage Adapter on a System Including                                         a Dynamically Loaded Adapter Driver"                                          "Method for the Hot Swap of a                                                                    08/943,078                                                                             MNFRAME.006A9                                     Network Adapter on a System                                                   Including a Dynamically Loaded                                                Adapter Driver"                                                               "Method for the Hot Swap of a Mass                                                               08/942,336                                                                             MNFRAME.006A10                                    Storage Adapter on a System Including                                         a Statically Loaded Adapter Driver"                                           "Method for the Hot Swap of a                                                                    08/942,459                                                                             MNFRAME.006A11                                    Network Adapter on a System                                                   Including a Statically Loaded Adapter                                         Driver"                                                                       "Method for the Hot Swap of a Mass                                                               08/942,458                                                                             MNFRAME.006A12                                    Storage Adapter on a Syetm Including                                          a Dynamically Loaded Adapter Driver"                                          "Method of Performing an Extensive                                                               08/942,463                                                                             MNFRAME.008A                                      Diagnostic Test in Conjunction with a                                         BIOS Test Routine"                                                            "Apparatus for Performing an                                                                     08/942,163                                                                             MNFRAME.009A                                      Extensive Diagnostic Test in                                                  Conjunction with a BIOS Test                                                  Routine"                                                                      "Configuration Manangement Method                                                                08/941,268                                                                             MNFRAME.010A                                      for Hot Adding and Hot Replacing                                              Devices"                                                                      "Configuration Management System                                                                 08/942,408                                                                             MNFRAME.011A                                      for Hot Adding and Hot Replacing                                              Devices"                                                                      "Apparatus for Interfacing Buses"                                                                08/942,382                                                                             MNFRAME.012A                                      "Method for Interfacing Buses"                                                                   08/942,413                                                                             MNFRAME.013A                                      "Computer Fan Speed Control Device"                                                              08/942,447                                                                             MNFRAME.016A                                      "Computer Fan Speed Control Method"                                                              08/942,216                                                                             MNFRAME.017A                                      "System for Powering Up and                                                                      08/943,076                                                                             MNFRAME.018A                                      Powering Down a Server"                                                       "Method of Powering Up and                                                                       08/943,077                                                                             MNFRAME.019A                                      Powering Down a Server"                                                       "System for Resetting a Server"                                                                  08/942,333                                                                             MNFRAME.020A                                      "Method of Resetting a Server"                                                                   08/942,405                                                                             MNFRAME.021A                                      "System for Displaying Flight                                                                    08/942,070                                                                             MNFRAME.022A                                      Recorder"                                                                     "Method of Displaying Flight                                                                     08/942,068                                                                             MNFRAME.023A                                      Recorder"                                                                     "Synchronous Communication                                                                       08/943,355                                                                             MNFRAME.024A                                      Interface"                                                                    "Synchronous Communication                                                                       08/942,004                                                                             MNFRAME.025A                                      Emulation"                                                                    "Software System Facilitating the                                                                08/942,317                                                                             MNFRAME.026A                                      Replacement or Insertion of Devices in                                        a Computer System"                                                            "Method for Facilitating the                                                                     08/942,316                                                                             MNFRAME.027A                                      Replacement or Insertion of Devices in                                        a Computer System"                                                            "System Management Graphical User                                                                08/943,357                                                                             MNFRAME.028A                                      Interface"                                                                    "Data Management System Supporting                                                               08/942,129                                                                             MNFRAME.030A                                      Hot Plug Operations on a Computer"                                            "Data Management Method Supporting                                                               08/942,124                                                                             MNFRAME.031A                                      Hot Plug Operations on a Computer"                                            "Alert Configurator and Manager"                                                                 08/942,005                                                                             MNFRAME.032A                                      "Managing Computer System Alerts"                                                                08/943,356                                                                             MNFRAME.033A                                      "Computer Fan Speed Control System"                                                              08/940,301                                                                             MNFRAME.034A                                      "Computer Fan Speed Control System                                                               08/941,267                                                                             MNFRAME.035A                                      Method"                                                                       "Black Box Recorder for Information                                                              08/942,381                                                                             MNFRAME.036A                                      System Events"                                                                "Method of Recording Information                                                                 08/942,164                                                                             MNFRAME.037A                                      System Events"                                                                "Method for Automatically Reporting a                                                            08/942,168                                                                             MNFRAME.040A                                      System Failure in a Server"                                                   "System for Automatically Reporting a                                                            08/942,384                                                                             MNFRAME.041A                                      "Expansion of PCI Bus Loading                                                                    08/942,404                                                                             MNFRAME.042A                                      Capacity"                                                                     "Method for Expanding PCI Bus                                                                    08/942,223                                                                             MNFRAME.043A                                      Loading Capacity"                                                             "System for Displaying System Status"                                                            08/942,347                                                                             MNFRAME.044A                                      "Method of Displaying System Status"                                                             08/942,071                                                                             MNFRAME.045A                                      "Fault Tolerant Computer System"                                                                 08/942,194                                                                             MNFRAME.046A                                      "Method for Hot Swapping of Network                                                              08/943,044                                                                             MNFRAME.047A                                      Components"                                                                   "A Method for Communicating a                                                                    08/942,221                                                                             MNFRAME.048A                                      Software Generated Pulse Waveform                                             Between Two Servers in a Network"                                             "A System for Communicating a                                                                    08/942,409                                                                             MNFRAME.049A                                      Software Generated Pulse Waveform                                             Between Two Servers in a Network"                                             "Method for Clustering Software                                                                  08/942,318                                                                             MNFRAME.050A                                      Applications"                                                                 "System for Clustering Software                                                                  08/942,411                                                                             MNFRAME.051A                                      Applications"                                                                 "Method for Automatically                                                                        08/942,319                                                                             MNFRAME.052A                                      Configuring a Server after Hot Add of                                         a Device"                                                                     "System for Automatically Configuring                                                            08/942,331                                                                             MNFRAME.053A                                      a Server after Hot Add of a Device"                                           "Method of Automatically Configuring                                                             08/942,412                                                                             MNFRAME.054A                                      and Formatting a Computer System                                              and Installing Software"                                                      "System for Automaticaaly Configuring                                                            08/941,955                                                                             MNFRAME.055A                                      and Formatting a Computer System                                              and Installing Software"                                                      "Determining Slot Numbers in a                                                                   08/942,462                                                                             MNFRAME.056A                                      Computer"                                                                     "System for Detecting Errors in a                                                                08/942,169                                                                             MNFRAME.058A                                      Network"                                                                      "Method of Detecting Errors in a                                                                 08/940,302                                                                             MNFRAME.059A                                      Network"                                                                      "System for Detecting Network Errors"                                                            08/942,407                                                                             MNFRAME.060A                                      "Method of Detecting Network Errors"                                                             08/942,573                                                                             MNFRAME.061A                                      __________________________________________________________________________

What is claimed is:
 1. A method for displaying information regardingcomponents in a computer network, comprising the acts of:providing aplurality of operational parameters about different components in acomputer network, said operational parameters further organized into aplurality of hierarchical levels; providing a plurality of forms whichenable the display and modification of one or more of said operationalparameters, each of said forms corresponding to one of said hierarchicallevels; displaying said hierarchical levels, in a first display pane;enabling the selection of one of said hierarchical levels via said firstdisplay pane; displaying said form corresponding to said one of saidhierarchical levels in a second display pane; enabling the selection ofanother one of said hierarchical levels; and replacing said formcorresponding to said one of said hierarchical levels with said formcorresponding to said another one of said hierarchical levels in saidsecond display pane.
 2. The method of claim 1 wherein said act ofdisplaying said hierarchical levels displays a subset of saidoperational parameters associated with said selected hierarchical level.3. The method of claim 1 wherein said hierarchical levels are defined ina management information base.
 4. The method of claim 1 wherein saidhierarchical levels are defined in a management information basecompatible with a Simple Network Management Protocol.
 5. The method ofclaim 1 further comprising the act of modifying one of said operationalparameters.
 6. The method of claim 5 further comprising the act ofupdating the status of said component corresponding to said modifiedoperational parameter.
 7. A method for displaying information regardingcomponents in a computer network, comprising:providing a plurality ofoperational parameters about different components in a computer network,said operational parameters further organized into a plurality ofhierarchical levels; providing a plurality of forms, each of said formsorganized to correspond to one of said hierarchical levels, each of saidforms further configured to provide descriptions of at least one of saidoperational parameters associated with said hierarchical levels and topermit modification of at least one of said operational parametersassociated with said hierarchical levels; displaying said hierarchicallevels in a first display pane; selecting one of said hierarchicallevels; displaying said form corresponding to said one of saidhierarchical levels in a second display pane; selecting of another oneof said hierarchical levels; and replacing said form corresponding tosaid one of said hierarchical levels with said form corresponding tosaid another one of said hierarchical levels in said second displaypane.
 8. The method of claim 7 wherein said descriptions display theunits of said operational parameters.
 9. The method of claim 7 whereinsaid descriptions display the name of the component associated with saidoperational parameter.
 10. The method of claim 7 wherein saiddescriptions display the name of a network server associated with saidoperational parameters.
 11. The method of claim 7 further comprising theact of organizing said operational parameters into different groupings.12. The method of claim 7 wherein said hierarchical levels include atleast one of said operational parameters.
 13. A method for displayinginformation regarding components in a computer network,comprising:providing a plurality of operational parameters aboutdifferent components in a computer network wherein some of saidoperational parameters are inaccessible and some of said operationalparameters are accessible and wherein said operational parameters arefurther organized into a plurality of hierarchical levels; providing aplurality of forms which are configured to exclude data about saidinaccessible operational parameters, each of said forms corresponding toone of said hierarchical levels; displaying said hierarchical levels ina first display pane; selecting one of said hierarchical levels; anddisplaying said form corresponding to said one of said hierarchicallevels in a second display pane and permitting modification of at leastone of said accessible operational parameters.
 14. The method of claim13 wherein said first display pane displays a subset of said accessibleoperational parameters in said selected hierarchical level.
 15. Themethod of claim 14 wherein subset of said accessible operationalparameters are organized into a group of canisters.
 16. The method ofclaim 14 further comprising the act of organizing said subset of saidaccessible operational parameters into a group of cooling systemparameters.
 17. The method of claim 14 further comprising the act oforganizing subset of said accessible operational parameters into a groupof temperature parameters.
 18. The method of claim 14 further comprisingthe act of organizing said subset of said accessible operationalparameters into a group of adapter parameters.
 19. The method of claim14 further comprising the act of organizing said subset of saidaccessible operational parameters into a group of driver parameters. 20.The method of claim 14 further comprising the act of organizing saidsubset of said accessible operational parameters into a group ofprocessor parameters.
 21. The method of claim 14 further comprising theact of organizing said subset of said accessible operational parametersinto a group of slot parameters.
 22. The method of claim 14 furthercomprising the act of organizing said subset of said accessibleoperational parameters into a group of slot fan parameters.